Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12f99b86fff1a6b4b4b3ca5a00d667a5915ce5f446221f6819dd3e447b5f4e6c

Tx prefix hash: ee1390319407c50326d4818bedbe62b68f9bda3d572a6a870c75c426c248db10
Tx public key: a4482af2dd6d61e3e3068da85bbf5a3c6163679dbce9585d241ece2ee275aae1
Timestamp: 1735563309 Timestamp [UCT]: 2024-12-30 12:55:09 Age [y:d:h:m:s]: 00:114:03:42:43
Block: 1186454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81375 RingCT/type: yes/0
Extra: 01a4482af2dd6d61e3e3068da85bbf5a3c6163679dbce9585d241ece2ee275aae1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7eef540b7df0678d6103001d7e05e85bfb46505a77c862c1f24eccd1c98bde 0.600000000000 1672935 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": 1186464, "vin": [ { "gen": { "height": 1186454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7eef540b7df0678d6103001d7e05e85bfb46505a77c862c1f24eccd1c98bde" } } ], "extra": [ 1, 164, 72, 42, 242, 221, 109, 97, 227, 227, 6, 141, 168, 91, 191, 90, 60, 97, 99, 103, 157, 188, 233, 88, 93, 36, 30, 206, 46, 226, 117, 170, 225, 2, 17, 0, 0, 0, 2, 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