Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc733f3da59690c7bd905da7d0e19e9359fcca540c23d95386cacaae048c4a6

Tx prefix hash: 768f2835fe85f1bc871cd968afa033e886f08c7489acd174953c3c5a3cbc9342
Tx public key: cb58f4da5a5740a6ee8476cc7a68fc3c7b07878afdc3b8820dc1d722dc122107
Timestamp: 1745674609 Timestamp [UCT]: 2025-04-26 13:36:49 Age [y:d:h:m:s]: 00:200:22:45:05
Block: 1269900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141326 RingCT/type: yes/0
Extra: 01cb58f4da5a5740a6ee8476cc7a68fc3c7b07878afdc3b8820dc1d722dc12210702110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0489dd8d63532c8a8c2f69448ec6006bb38c885cb65ba8486db49e7d5a70160d 0.600000000000 1757139 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": 1269910, "vin": [ { "gen": { "height": 1269900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0489dd8d63532c8a8c2f69448ec6006bb38c885cb65ba8486db49e7d5a70160d" } } ], "extra": [ 1, 203, 88, 244, 218, 90, 87, 64, 166, 238, 132, 118, 204, 122, 104, 252, 60, 123, 7, 135, 138, 253, 195, 184, 130, 13, 193, 215, 34, 220, 18, 33, 7, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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