Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9028160e19f5dba381a564e5c20bec4c322864c90b197451bccb8fc03486d39d

Tx prefix hash: e7fb4b657237039a39596777b5d66bf18ae4c69dcbe79ed5bf562cb7d3b5bf14
Tx public key: b89ae14f992bbb1f18e87b6b3ca125c926d8b3c0051e07986ace2ec589064556
Timestamp: 1728918820 Timestamp [UCT]: 2024-10-14 15:13:40 Age [y:d:h:m:s]: 00:101:18:33:29
Block: 1131506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72699 RingCT/type: yes/0
Extra: 01b89ae14f992bbb1f18e87b6b3ca125c926d8b3c0051e07986ace2ec589064556021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d2f1fd9c8e08921689a825fb92f8335d1164ba8db0814062331bf82e01dfb83 0.600000000000 1614409 of 15

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": 1131516, "vin": [ { "gen": { "height": 1131506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d2f1fd9c8e08921689a825fb92f8335d1164ba8db0814062331bf82e01dfb83" } } ], "extra": [ 1, 184, 154, 225, 79, 153, 43, 187, 31, 24, 232, 123, 107, 60, 161, 37, 201, 38, 216, 179, 192, 5, 30, 7, 152, 106, 206, 46, 197, 137, 6, 69, 86, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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