Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eb53471a60524d9644aef6dba1cee28bf49cbc71e728daafaea6e4ee1ce5b6d

Tx prefix hash: 220f2197d7f93e29e76bcc04050c4734de842b714635796a304186d73ef0ca60
Tx public key: a2e5133fd15a8d31c021ca40ff39032f82f6ab15819baf0947e21681009665b4
Timestamp: 1576424269 Timestamp [UCT]: 2019-12-15 15:37:49 Age [y:d:h:m:s]: 04:348:06:53:34
Block: 27305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135112 RingCT/type: yes/0
Extra: 01a2e5133fd15a8d31c021ca40ff39032f82f6ab15819baf0947e21681009665b40211000000149159db1e000000000000000000

1 output(s) for total of 498.342660448000 dcy

stealth address amount amount idx
00: 99534d6ec60bb1e6201e5b8984cb98084a2a82c0d29f142a5d83b752e1a7a6e9 498.342660448000 45301 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": 27315, "vin": [ { "gen": { "height": 27305 } } ], "vout": [ { "amount": 498342660448, "target": { "key": "99534d6ec60bb1e6201e5b8984cb98084a2a82c0d29f142a5d83b752e1a7a6e9" } } ], "extra": [ 1, 162, 229, 19, 63, 209, 90, 141, 49, 192, 33, 202, 64, 255, 57, 3, 47, 130, 246, 171, 21, 129, 155, 175, 9, 71, 226, 22, 129, 0, 150, 101, 180, 2, 17, 0, 0, 0, 20, 145, 89, 219, 30, 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