Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1db9c4d40526772b32a92caac97adac5fbca193f45a66266a2a20f7b010aa774

Tx prefix hash: 6d6ee982f0d28540764cce60fe741461bf1bf4b52f46d346e9b9a8b9b84503d6
Tx public key: 0eaa1c9b3bdded440826f8d375284bf05c40a6573a68ab5aca54d30e57598fc9
Timestamp: 1723523862 Timestamp [UCT]: 2024-08-13 04:37:42 Age [y:d:h:m:s]: 00:289:04:04:08
Block: 1086767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206607 RingCT/type: yes/0
Extra: 010eaa1c9b3bdded440826f8d375284bf05c40a6573a68ab5aca54d30e57598fc902110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6ad9a69c34af8bdbd28d758916963d0d921521cc30f83da92333503bb4d3f3d 0.600000000000 1561366 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": 1086777, "vin": [ { "gen": { "height": 1086767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6ad9a69c34af8bdbd28d758916963d0d921521cc30f83da92333503bb4d3f3d" } } ], "extra": [ 1, 14, 170, 28, 155, 59, 221, 237, 68, 8, 38, 248, 211, 117, 40, 75, 240, 92, 64, 166, 87, 58, 104, 171, 90, 202, 84, 211, 14, 87, 89, 143, 201, 2, 17, 0, 0, 0, 13, 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