Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1292eb9694941db50e89fde5b5a5f99db91bd702a58535019fc0cd324a47bff2

Tx prefix hash: b18afd1f135d283e68143cf8565da0d5126a716926bc0f20938d51449f1cf80f
Tx public key: f4c6768da0dd7cd9707ee36081f7dc2246f942063e8908f24230a2be2ac7081e
Timestamp: 1578920751 Timestamp [UCT]: 2020-01-13 13:05:51 Age [y:d:h:m:s]: 05:296:12:13:19
Block: 44627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359827 RingCT/type: yes/0
Extra: 01f4c6768da0dd7cd9707ee36081f7dc2246f942063e8908f24230a2be2ac7081e02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 436.649597641000 dcy

stealth address amount amount idx
00: b2b2b2b87833ee8c6a568ee4aeff05ced149bcf96a5013689fe982dfa77d39c2 436.649597641000 81270 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": 44637, "vin": [ { "gen": { "height": 44627 } } ], "vout": [ { "amount": 436649597641, "target": { "key": "b2b2b2b87833ee8c6a568ee4aeff05ced149bcf96a5013689fe982dfa77d39c2" } } ], "extra": [ 1, 244, 198, 118, 141, 160, 221, 124, 217, 112, 126, 227, 96, 129, 247, 220, 34, 70, 249, 66, 6, 62, 137, 8, 242, 66, 48, 162, 190, 42, 199, 8, 30, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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