Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 048d3f4422be9cf2bffe0b3270e8557777b39d8424dcaf7d96e11460a85a4cbe

Tx prefix hash: ad8ae6d80fba4e63407aaff6c6baf55b11fabac2cf410207390fed22ec6a43e9
Tx public key: 7930c7f3647326b6549504d6023e0a1547350f46e936831aa5ca3a4e2b12cccd
Timestamp: 1713741394 Timestamp [UCT]: 2024-04-21 23:16:34 Age [y:d:h:m:s]: 00:312:10:53:51
Block: 1005659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223343 RingCT/type: yes/0
Extra: 017930c7f3647326b6549504d6023e0a1547350f46e936831aa5ca3a4e2b12cccd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3fe79ad37f1638a1ac620c3466911200b2abf9c90405812e827c5771f85877 0.600000000000 1466417 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": 1005669, "vin": [ { "gen": { "height": 1005659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3fe79ad37f1638a1ac620c3466911200b2abf9c90405812e827c5771f85877" } } ], "extra": [ 1, 121, 48, 199, 243, 100, 115, 38, 182, 84, 149, 4, 214, 2, 62, 10, 21, 71, 53, 15, 70, 233, 54, 131, 26, 165, 202, 58, 78, 43, 18, 204, 205, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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