Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b97c52710603f5c1cba7c393c2377a3e2e06a7b25d89371dc07f7bf8555821f

Tx prefix hash: 0e7d52f96c9ea5b2c2579a0ecd48751fe3c15bf178842ac265bc35b99e2753b7
Tx public key: 566b5dc3e42ff86f9f064bf36b088113d0ab769bad168a1b4b1d3da05735f1fb
Timestamp: 1736652831 Timestamp [UCT]: 2025-01-12 03:33:51 Age [y:d:h:m:s]: 00:160:00:55:03
Block: 1195472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114040 RingCT/type: yes/0
Extra: 01566b5dc3e42ff86f9f064bf36b088113d0ab769bad168a1b4b1d3da05735f1fb0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c262e8ffb6d79e5da892be7c6425d3e13fbb6c54f6c9311d05c3133e36d07272 0.600000000000 1682063 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": 1195482, "vin": [ { "gen": { "height": 1195472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c262e8ffb6d79e5da892be7c6425d3e13fbb6c54f6c9311d05c3133e36d07272" } } ], "extra": [ 1, 86, 107, 93, 195, 228, 47, 248, 111, 159, 6, 75, 243, 107, 8, 129, 19, 208, 171, 118, 155, 173, 22, 138, 27, 75, 29, 61, 160, 87, 53, 241, 251, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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