Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fd10dd77b096363b9ffd09032e2635af3a2dbf7549ddf982db6bd6e687a618c

Tx prefix hash: 497dc3e5370483433f5e9117b7ef69ad75d5bbb1a85bbefbfcb2bba8c2b33bc1
Tx public key: 6c03a41f0a062eed47a8040931775de63ba9d06ce636242d7804d4a2fcaa4a04
Timestamp: 1716707079 Timestamp [UCT]: 2024-05-26 07:04:39 Age [y:d:h:m:s]: 00:363:02:50:50
Block: 1030271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259552 RingCT/type: yes/0
Extra: 016c03a41f0a062eed47a8040931775de63ba9d06ce636242d7804d4a2fcaa4a0402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 498a84665172afe0afce6362b3af6fe6e77f5ff3ee5912d881928cdf4f1a5b86 0.600000000000 1498526 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": 1030281, "vin": [ { "gen": { "height": 1030271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "498a84665172afe0afce6362b3af6fe6e77f5ff3ee5912d881928cdf4f1a5b86" } } ], "extra": [ 1, 108, 3, 164, 31, 10, 6, 46, 237, 71, 168, 4, 9, 49, 119, 93, 230, 59, 169, 208, 108, 230, 54, 36, 45, 120, 4, 212, 162, 252, 170, 74, 4, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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