Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da6f739a096aa8efabaf6442e0c0e4b7411d28997100479a0ea91d6a10bc949

Tx prefix hash: 8977330a9f6f52f7f7a7efc62b1508ef93ab0cc4a05014871b0fc17ad75689a6
Tx public key: e8bc8ee30e64db218ea764b17c7be5a40eb2228fa747b02abef60256470c9014
Timestamp: 1581951089 Timestamp [UCT]: 2020-02-17 14:51:29 Age [y:d:h:m:s]: 04:289:07:58:54
Block: 66929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099081 RingCT/type: yes/0
Extra: 01e8bc8ee30e64db218ea764b17c7be5a40eb2228fa747b02abef60256470c9014021100000001724f989b000000000000000000

1 output(s) for total of 368.330131129000 dcy

stealth address amount amount idx
00: f705e60eab46b9f116ebd47a100c8a11b4473200c1f2c1700a29e9a4443c8e1e 368.330131129000 123188 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": 66939, "vin": [ { "gen": { "height": 66929 } } ], "vout": [ { "amount": 368330131129, "target": { "key": "f705e60eab46b9f116ebd47a100c8a11b4473200c1f2c1700a29e9a4443c8e1e" } } ], "extra": [ 1, 232, 188, 142, 227, 14, 100, 219, 33, 142, 167, 100, 177, 124, 123, 229, 164, 14, 178, 34, 143, 167, 71, 176, 42, 190, 246, 2, 86, 71, 12, 144, 20, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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