Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f10c51452c1dc775bd1a77e333cadcd7892d563f68d00e035b3bc8f9732c67b4

Tx prefix hash: 4e99f8316206b5f024d296ffd6f6be9bdab16ceffc129228589cbdcecbc23e0f
Tx public key: e4597ce9f8b6d5c457bd89f586ab91d4df0f8485c3ecd1d6170d42f4de4003bb
Timestamp: 1699937276 Timestamp [UCT]: 2023-11-14 04:47:56 Age [y:d:h:m:s]: 01:165:12:02:02
Block: 891237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379472 RingCT/type: yes/0
Extra: 01e4597ce9f8b6d5c457bd89f586ab91d4df0f8485c3ecd1d6170d42f4de4003bb021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.683851565000 dcy

stealth address amount amount idx
00: 1126fdf115eaaba9a4d8bd2a12b7b8c84848f3f8de454e01c367ac3e62f20997 0.683851565000 1347272 of 0

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": 891247, "vin": [ { "gen": { "height": 891237 } } ], "vout": [ { "amount": 683851565, "target": { "key": "1126fdf115eaaba9a4d8bd2a12b7b8c84848f3f8de454e01c367ac3e62f20997" } } ], "extra": [ 1, 228, 89, 124, 233, 248, 182, 213, 196, 87, 189, 137, 245, 134, 171, 145, 212, 223, 15, 132, 133, 195, 236, 209, 214, 23, 13, 66, 244, 222, 64, 3, 187, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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