Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a010e19699f8c22f05a4c8392ea1efb1596ba09b573970e14578942337de7941

Tx prefix hash: c01265bdeedb2f679784db8274ce5f4b2d155be3393ebd46f15a78b659d3ea7f
Tx public key: a93dca22e25a8a6a21efd073a152b169a3c735dfb56bf2eed47019dd91e77ad1
Timestamp: 1722535413 Timestamp [UCT]: 2024-08-01 18:03:33 Age [y:d:h:m:s]: 00:251:16:53:04
Block: 1078569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179801 RingCT/type: yes/0
Extra: 01a93dca22e25a8a6a21efd073a152b169a3c735dfb56bf2eed47019dd91e77ad1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fcd0b527115c4db116a63e047cad01fd332a99f7a3d2a738d12eece9caa1f4f 0.600000000000 1551164 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": 1078579, "vin": [ { "gen": { "height": 1078569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fcd0b527115c4db116a63e047cad01fd332a99f7a3d2a738d12eece9caa1f4f" } } ], "extra": [ 1, 169, 61, 202, 34, 226, 90, 138, 106, 33, 239, 208, 115, 161, 82, 177, 105, 163, 199, 53, 223, 181, 107, 242, 238, 212, 112, 25, 221, 145, 231, 122, 209, 2, 17, 0, 0, 0, 3, 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