Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57ba00c66b7fa5f9d75f516ca1ed1226b7c971bd87a9fd21b49d3d2d379e2b98

Tx prefix hash: fa1604f84f2824475688222ce949390a205e92a32478392815e22ba83051a78f
Tx public key: eb0b233a67100e6ba807b24f8d87ebe446c83d79e3871d6ae852de5b5a0a93d2
Timestamp: 1735826553 Timestamp [UCT]: 2025-01-02 14:02:33 Age [y:d:h:m:s]: 00:125:09:42:42
Block: 1188636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89434 RingCT/type: yes/0
Extra: 01eb0b233a67100e6ba807b24f8d87ebe446c83d79e3871d6ae852de5b5a0a93d20211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 000b93dee9d13928bb20dd3f5bd92d870d6337d2ad0f3e3b8baad238ede8bd87 0.600000000000 1675139 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": 1188646, "vin": [ { "gen": { "height": 1188636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "000b93dee9d13928bb20dd3f5bd92d870d6337d2ad0f3e3b8baad238ede8bd87" } } ], "extra": [ 1, 235, 11, 35, 58, 103, 16, 14, 107, 168, 7, 178, 79, 141, 135, 235, 228, 70, 200, 61, 121, 227, 135, 29, 106, 232, 82, 222, 91, 90, 10, 147, 210, 2, 17, 0, 0, 0, 3, 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