Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f91c9c4d83b18d9673065727e3a314baeeaa5999d034673e8867a4688c71f9b

Tx prefix hash: 23e8bb396053e4cd2a49f5f51f3ad8af56847fce4850b72a1e9206b9dfc1d30e
Tx public key: ceac79fdd380d3b5b66e27838c1081077ac4a6b2921c8f39f8813951d46fdf44
Timestamp: 1741625133 Timestamp [UCT]: 2025-03-10 16:45:33 Age [y:d:h:m:s]: 00:255:15:01:09
Block: 1236382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180418 RingCT/type: yes/0
Extra: 01ceac79fdd380d3b5b66e27838c1081077ac4a6b2921c8f39f8813951d46fdf44021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb98f8871b1facd4a706240835cf60bb147cf0b5dc1aed7019688a328d250ab2 0.600000000000 1723329 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": 1236392, "vin": [ { "gen": { "height": 1236382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb98f8871b1facd4a706240835cf60bb147cf0b5dc1aed7019688a328d250ab2" } } ], "extra": [ 1, 206, 172, 121, 253, 211, 128, 211, 181, 182, 110, 39, 131, 140, 16, 129, 7, 122, 196, 166, 178, 146, 28, 143, 57, 248, 129, 57, 81, 212, 111, 223, 68, 2, 17, 0, 0, 0, 3, 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