Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 813410a8e418c3b0a5ddd9ef3a7e555adec0430477992669956eb36ac09f9b9c

Tx prefix hash: 51e27e19d57af338cda661ef169190630fbf38240c0bba62a4cc09716fb89a71
Tx public key: 2b4a879cfe9da1f9ff1110d7d1459c8b6077f73d7625a6d330341bed270769fd
Timestamp: 1720441658 Timestamp [UCT]: 2024-07-08 12:27:38 Age [y:d:h:m:s]: 00:275:14:06:37
Block: 1061223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196899 RingCT/type: yes/0
Extra: 012b4a879cfe9da1f9ff1110d7d1459c8b6077f73d7625a6d330341bed270769fd021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e003b4590379800c7760f9227d416a12bd3cd5e2c80b9ed3a6251d8eae941f8 0.600000000000 1531714 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": 1061233, "vin": [ { "gen": { "height": 1061223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e003b4590379800c7760f9227d416a12bd3cd5e2c80b9ed3a6251d8eae941f8" } } ], "extra": [ 1, 43, 74, 135, 156, 254, 157, 161, 249, 255, 17, 16, 215, 209, 69, 156, 139, 96, 119, 247, 61, 118, 37, 166, 211, 48, 52, 27, 237, 39, 7, 105, 253, 2, 17, 0, 0, 0, 6, 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