Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c32f5e5296bc257bcee4065af1569c19e111ab05ba0f3de46f81c4c85e0448b

Tx prefix hash: b52e45568760855eac97c183207ac7053b1dc9486fd1148cb0e6de9f414b3695
Tx public key: dc68d6e8f379641c79167635e805e2ed5a77d050e698b89eab21cd9d8c7f70dc
Timestamp: 1725645523 Timestamp [UCT]: 2024-09-06 17:58:43 Age [y:d:h:m:s]: 00:209:22:48:35
Block: 1104361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149893 RingCT/type: yes/0
Extra: 01dc68d6e8f379641c79167635e805e2ed5a77d050e698b89eab21cd9d8c7f70dc021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2df177733ad546b1e373f93d71f8340eb73246d4855bf0e5d3bc50eb8dc49fe 0.600000000000 1581474 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": 1104371, "vin": [ { "gen": { "height": 1104361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2df177733ad546b1e373f93d71f8340eb73246d4855bf0e5d3bc50eb8dc49fe" } } ], "extra": [ 1, 220, 104, 214, 232, 243, 121, 100, 28, 121, 22, 118, 53, 232, 5, 226, 237, 90, 119, 208, 80, 230, 152, 184, 158, 171, 33, 205, 157, 140, 127, 112, 220, 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