Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450fb9a0286a8900a2373e74910a8ca43e0a7bf1fefa8703b61fcc8d4bcf2d14

Tx prefix hash: 6cf581b63f9da54fe7409fc3dba5eba29c2e64db4625b0411ab6ba6079eab109
Tx public key: 01eaea4375c387a2eaa482a8766bd900995362dfe834dc71f95d70f3c29c54e9
Timestamp: 1703127108 Timestamp [UCT]: 2023-12-21 02:51:48 Age [y:d:h:m:s]: 01:180:00:26:14
Block: 917686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389694 RingCT/type: yes/0
Extra: 0101eaea4375c387a2eaa482a8766bd900995362dfe834dc71f95d70f3c29c54e9021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5903ffe3fcc0faba3858c7bd46a65c759f6114d1af21bf34af471485c8d72e7c 0.600000000000 1375268 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": 917696, "vin": [ { "gen": { "height": 917686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5903ffe3fcc0faba3858c7bd46a65c759f6114d1af21bf34af471485c8d72e7c" } } ], "extra": [ 1, 1, 234, 234, 67, 117, 195, 135, 162, 234, 164, 130, 168, 118, 107, 217, 0, 153, 83, 98, 223, 232, 52, 220, 113, 249, 93, 112, 243, 194, 156, 84, 233, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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