Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 022a85c07415c2b5dbfe460e508a52027b42403e1daef33f8fdb6f8bd1a38dd5

Tx prefix hash: ab0daa24388a4efa4d71c683f3bc787b8af1fcb4601f97f6ad348ad067b5322f
Tx public key: 6472f850aeb3a1bf8875fd5a21b823afe0aeba1ac5b8e235b14bd3a38bef427f
Timestamp: 1728063486 Timestamp [UCT]: 2024-10-04 17:38:06 Age [y:d:h:m:s]: 00:161:07:15:33
Block: 1124416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115079 RingCT/type: yes/0
Extra: 016472f850aeb3a1bf8875fd5a21b823afe0aeba1ac5b8e235b14bd3a38bef427f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2f1005ccc40e34f719307e5f65c58ee517d192515e6ccdfcfb8dcb3d28aec9b 0.600000000000 1607035 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": 1124426, "vin": [ { "gen": { "height": 1124416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2f1005ccc40e34f719307e5f65c58ee517d192515e6ccdfcfb8dcb3d28aec9b" } } ], "extra": [ 1, 100, 114, 248, 80, 174, 179, 161, 191, 136, 117, 253, 90, 33, 184, 35, 175, 224, 174, 186, 26, 197, 184, 226, 53, 177, 75, 211, 163, 139, 239, 66, 127, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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