Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca966a4b077b1ba2f709a3458cff1ca90d68e38cca0bae34e962629c6b75527c

Tx prefix hash: 72558ab155db4f86a5f222c502ea0d9427fd35bd9f3d1979f22301fd1cd7a4be
Tx public key: 5c37a729ad5721fd3311f70f3cd4bf97ddd6555981e0e6af6af1ecf5ca50765b
Timestamp: 1727838677 Timestamp [UCT]: 2024-10-02 03:11:17 Age [y:d:h:m:s]: 00:112:08:26:17
Block: 1122551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80272 RingCT/type: yes/0
Extra: 015c37a729ad5721fd3311f70f3cd4bf97ddd6555981e0e6af6af1ecf5ca50765b02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 434a43aa34a3c9f57057f5157bf03a6598e40164a17c735ff6235d21e7ef2c59 0.600000000000 1605016 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": 1122561, "vin": [ { "gen": { "height": 1122551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "434a43aa34a3c9f57057f5157bf03a6598e40164a17c735ff6235d21e7ef2c59" } } ], "extra": [ 1, 92, 55, 167, 41, 173, 87, 33, 253, 51, 17, 247, 15, 60, 212, 191, 151, 221, 214, 85, 89, 129, 224, 230, 175, 106, 241, 236, 245, 202, 80, 118, 91, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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