Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7496476c445a9c808445750c571424f0a39ec6ae9f3c63a6b664da83540b88ae

Tx prefix hash: ca613869dc02c8fc5edeb38a67fef5783cf99048cf182a70d4e7066fff3cbbdf
Tx public key: 6f148b92f1d449b95b2f00a4f1c4b769066389be2857042c633de96609722d13
Timestamp: 1577708144 Timestamp [UCT]: 2019-12-30 12:15:44 Age [y:d:h:m:s]: 05:000:07:25:16
Block: 35010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150205 RingCT/type: yes/0
Extra: 016f148b92f1d449b95b2f00a4f1c4b769066389be2857042c633de96609722d13021100000001d81c26c0000000000000000000

1 output(s) for total of 469.892151975000 dcy

stealth address amount amount idx
00: 4c96b3a0ddcc95aaf96d93a07df5dc1ecf6ca127c8660cfb32165566a88edb5e 469.892151975000 58985 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": 35020, "vin": [ { "gen": { "height": 35010 } } ], "vout": [ { "amount": 469892151975, "target": { "key": "4c96b3a0ddcc95aaf96d93a07df5dc1ecf6ca127c8660cfb32165566a88edb5e" } } ], "extra": [ 1, 111, 20, 139, 146, 241, 212, 73, 185, 91, 47, 0, 164, 241, 196, 183, 105, 6, 99, 137, 190, 40, 87, 4, 44, 99, 61, 233, 102, 9, 114, 45, 19, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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