Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 416aedd1293f317fec3164493d881fbb83d4ef3219e9daf9be7c42a151d9ed04

Tx prefix hash: 083bccb2b55f0f78b50e5950b685d96438c69e50932d8b09b5d75e62f4f4a738
Tx public key: 067a80bd244d6daacb2f91a00c1dc046a87bfe83e5435bdb2322ba2db3826ab0
Timestamp: 1736260957 Timestamp [UCT]: 2025-01-07 14:42:37 Age [y:d:h:m:s]: 00:297:06:48:24
Block: 1192234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209960 RingCT/type: yes/0
Extra: 01067a80bd244d6daacb2f91a00c1dc046a87bfe83e5435bdb2322ba2db3826ab0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b538d947d482ada427f78d9ec9dad5af496fc419e4e7a53ebd2102f45937d933 0.600000000000 1678783 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": 1192244, "vin": [ { "gen": { "height": 1192234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b538d947d482ada427f78d9ec9dad5af496fc419e4e7a53ebd2102f45937d933" } } ], "extra": [ 1, 6, 122, 128, 189, 36, 77, 109, 170, 203, 47, 145, 160, 12, 29, 192, 70, 168, 123, 254, 131, 229, 67, 91, 219, 35, 34, 186, 45, 179, 130, 106, 176, 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