Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291c5880c8d0dd5b4c7d773fb67c1c650710ebc319c303e78776db82f201172a

Tx prefix hash: d4eb21053edd5bf00db35d48affc27b55e5e9b03241aaeb400ad4b66134c38fb
Tx public key: 6745b6e3603122490496d966a3b199d5cd1b8a882c36789dce9d18e118b44c43
Timestamp: 1729831041 Timestamp [UCT]: 2024-10-25 04:37:21 Age [y:d:h:m:s]: 00:185:10:38:56
Block: 1139023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132358 RingCT/type: yes/0
Extra: 016745b6e3603122490496d966a3b199d5cd1b8a882c36789dce9d18e118b44c43021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96ea4a2e2a2b6dd3aa85b17c2428d9ba7e92feecbfeca879746ecbc609b7dd9b 0.600000000000 1622776 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": 1139033, "vin": [ { "gen": { "height": 1139023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96ea4a2e2a2b6dd3aa85b17c2428d9ba7e92feecbfeca879746ecbc609b7dd9b" } } ], "extra": [ 1, 103, 69, 182, 227, 96, 49, 34, 73, 4, 150, 217, 102, 163, 177, 153, 213, 205, 27, 138, 136, 44, 54, 120, 157, 206, 157, 24, 225, 24, 180, 76, 67, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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