Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 940624bac38d79d120ca1b49787a99fccf2992b9cda14f9b9277f942b74af967

Tx prefix hash: 655f6a918ef16842dfea2bf0ba46df21b71cf7739c7a422dba34c3f1a628719a
Tx public key: ec7fecd274db19ea23f3a116d8ab320e9e94cca3bb6fd424857935c280ab9f69
Timestamp: 1657215066 Timestamp [UCT]: 2022-07-07 17:31:06 Age [y:d:h:m:s]: 02:257:02:44:55
Block: 538750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704898 RingCT/type: yes/0
Extra: 01ec7fecd274db19ea23f3a116d8ab320e9e94cca3bb6fd424857935c280ab9f6902110000000e5eb576c5000000000000000000

1 output(s) for total of 10.066946324000 dcy

stealth address amount amount idx
00: 5692dda11259a8197d37b3b19b0a926c6c68f94315b637148f4ad86d8e3eb6b4 10.066946324000 968787 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 538760, "vin": [ { "gen": { "height": 538750 } } ], "vout": [ { "amount": 10066946324, "target": { "key": "5692dda11259a8197d37b3b19b0a926c6c68f94315b637148f4ad86d8e3eb6b4" } } ], "extra": [ 1, 236, 127, 236, 210, 116, 219, 25, 234, 35, 243, 161, 22, 216, 171, 50, 14, 158, 148, 204, 163, 187, 111, 212, 36, 133, 121, 53, 194, 128, 171, 159, 105, 2, 17, 0, 0, 0, 14, 94, 181, 118, 197, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8