Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4501d764d0471e48ae5ece5bf52dddf3c27849c7e0f093127cdc841eef80399

Tx prefix hash: 41e071ba79650771077a000d60495e0aab1c86cfe2b0ced8f2a416d0164c83dd
Tx public key: 772b5465ec648db2d4af1b45fcc4ce25c5b5fe853b4268100649bec951e845db
Timestamp: 1700941877 Timestamp [UCT]: 2023-11-25 19:51:17 Age [y:d:h:m:s]: 01:054:23:46:42
Block: 899552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300658 RingCT/type: yes/0
Extra: 01772b5465ec648db2d4af1b45fcc4ce25c5b5fe853b4268100649bec951e845db02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.641816365000 dcy

stealth address amount amount idx
00: d3de9e2945f3fd707ac891d35a585856283bdb823048a07bc55ef66ec275b8d4 0.641816365000 1356011 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": 899562, "vin": [ { "gen": { "height": 899552 } } ], "vout": [ { "amount": 641816365, "target": { "key": "d3de9e2945f3fd707ac891d35a585856283bdb823048a07bc55ef66ec275b8d4" } } ], "extra": [ 1, 119, 43, 84, 101, 236, 100, 141, 178, 212, 175, 27, 69, 252, 196, 206, 37, 197, 181, 254, 133, 59, 66, 104, 16, 6, 73, 190, 201, 81, 232, 69, 219, 2, 17, 0, 0, 0, 10, 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