Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92194c1dfd58cbb71334a01def63b4724bdc154d22941768d346ae42247fab7f

Tx prefix hash: e30612e89e8ba23d918b4d0c075e54e24642067ca7694f31a6cd484c6c5785fc
Tx public key: 8fb1a4add5a20d9baa53a051fe4be2076574964afc39e00b0dd886ab9c378a16
Timestamp: 1736175914 Timestamp [UCT]: 2025-01-06 15:05:14 Age [y:d:h:m:s]: 00:093:23:59:03
Block: 1191545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66948 RingCT/type: yes/0
Extra: 018fb1a4add5a20d9baa53a051fe4be2076574964afc39e00b0dd886ab9c378a16021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42404ef1fdded6b26053e48593749038e6a9f1f54211b1fd163a51a5b7b27b01 0.600000000000 1678084 of 15

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": 1191555, "vin": [ { "gen": { "height": 1191545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42404ef1fdded6b26053e48593749038e6a9f1f54211b1fd163a51a5b7b27b01" } } ], "extra": [ 1, 143, 177, 164, 173, 213, 162, 13, 155, 170, 83, 160, 81, 254, 75, 226, 7, 101, 116, 150, 74, 252, 57, 224, 11, 13, 216, 134, 171, 156, 55, 138, 22, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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