Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87fe188dd09717b31a5120af1c6c0f78467f8c30c201a9098211ffe93de1ad7

Tx prefix hash: d1b0b6f71ea89dd16c39be1b2435dc6c5e4deec8588fcdba83f2670fbc0b123f
Tx public key: 0d0baabb1017eb21697029d9bafd1275e626058c702b4fb2fe2ff5034818c1f4
Timestamp: 1731172429 Timestamp [UCT]: 2024-11-09 17:13:49 Age [y:d:h:m:s]: 00:222:03:27:40
Block: 1150101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158491 RingCT/type: yes/0
Extra: 010d0baabb1017eb21697029d9bafd1275e626058c702b4fb2fe2ff5034818c1f4021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89688084432c7928a9a787023cb8cc6194d4c5d6daa5cd30e2fe782f4ff966d3 0.600000000000 1635308 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": 1150111, "vin": [ { "gen": { "height": 1150101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89688084432c7928a9a787023cb8cc6194d4c5d6daa5cd30e2fe782f4ff966d3" } } ], "extra": [ 1, 13, 11, 170, 187, 16, 23, 235, 33, 105, 112, 41, 217, 186, 253, 18, 117, 230, 38, 5, 140, 112, 43, 79, 178, 254, 47, 245, 3, 72, 24, 193, 244, 2, 17, 0, 0, 0, 1, 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