Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17e14319c4c132dd2a5d25dc554ea7e9ba53e3acec34554d9ebd9acd811ded3c

Tx prefix hash: c5ad951dd8fd76da8b59cdb53f13d92c3df5fd08c68b39a7dcbd7412d6733d20
Tx public key: 8ba2609a0b7f9df3379d542cbf24287969b12ee8580b2c7236b36a6799593e3b
Timestamp: 1582946024 Timestamp [UCT]: 2020-02-29 03:13:44 Age [y:d:h:m:s]: 04:364:03:36:24
Block: 73753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153718 RingCT/type: yes/0
Extra: 018ba2609a0b7f9df3379d542cbf24287969b12ee8580b2c7236b36a6799593e3b02110000000d4ac5aa02000000000000000000

1 output(s) for total of 349.652143113000 dcy

stealth address amount amount idx
00: 7633f62f128076dc3d9f96f4b32fd6c1fe61d0b9850a984916758fab9b3098e5 349.652143113000 136142 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": 73763, "vin": [ { "gen": { "height": 73753 } } ], "vout": [ { "amount": 349652143113, "target": { "key": "7633f62f128076dc3d9f96f4b32fd6c1fe61d0b9850a984916758fab9b3098e5" } } ], "extra": [ 1, 139, 162, 96, 154, 11, 127, 157, 243, 55, 157, 84, 44, 191, 36, 40, 121, 105, 177, 46, 232, 88, 11, 44, 114, 54, 179, 106, 103, 153, 89, 62, 59, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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