Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0211245b449c4ab03c2f3e9b622c8094cb7b365f1c1038810cbd5cca1e3252a9

Tx prefix hash: 7003cc96a9bf336973e824eecc159fc159fbe337a24aab9681937e9852ae8d54
Tx public key: a76a3bd11bbf5762dc8e4997077dbdb5d7e6918e0a393fb27e844e35f1ae3767
Timestamp: 1723129154 Timestamp [UCT]: 2024-08-08 14:59:14 Age [y:d:h:m:s]: 00:240:07:31:58
Block: 1083490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171642 RingCT/type: yes/0
Extra: 01a76a3bd11bbf5762dc8e4997077dbdb5d7e6918e0a393fb27e844e35f1ae376702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb4ec2efa061b915bea02b91d7966302c1a6d81b0567e18c9a498f141f6a2ed 0.600000000000 1557433 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": 1083500, "vin": [ { "gen": { "height": 1083490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb4ec2efa061b915bea02b91d7966302c1a6d81b0567e18c9a498f141f6a2ed" } } ], "extra": [ 1, 167, 106, 59, 209, 27, 191, 87, 98, 220, 142, 73, 151, 7, 125, 189, 181, 215, 230, 145, 142, 10, 57, 63, 178, 126, 132, 78, 53, 241, 174, 55, 103, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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