Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c3a29bb16ce1baff26166fc4148ffef0f3d151c4a58576a5591168bb64c965

Tx prefix hash: 50d8a4d829b9522329bc3ed7f26110894a9825f65fe6f8e564d8c5ab8fd4fc3f
Tx public key: 25a4fd8a5e09edb9d6106f38bcd1630b636c419f1d737ca1ea3f927663d3e8f1
Timestamp: 1738257823 Timestamp [UCT]: 2025-01-30 17:23:43 Age [y:d:h:m:s]: 00:042:05:57:02
Block: 1208497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30233 RingCT/type: yes/0
Extra: 0125a4fd8a5e09edb9d6106f38bcd1630b636c419f1d737ca1ea3f927663d3e8f10211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1aa343db79d28c556f780425763445550da0a689dca0a8cb7f5af328ea5cc6a 0.600000000000 1695230 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": 1208507, "vin": [ { "gen": { "height": 1208497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1aa343db79d28c556f780425763445550da0a689dca0a8cb7f5af328ea5cc6a" } } ], "extra": [ 1, 37, 164, 253, 138, 94, 9, 237, 185, 214, 16, 111, 56, 188, 209, 99, 11, 99, 108, 65, 159, 29, 115, 124, 161, 234, 63, 146, 118, 99, 211, 232, 241, 2, 17, 0, 0, 0, 6, 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