Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7bf347b1e945bc51b2b212d03e1d769163f7a4e467eeb0615d6c30f8d6b015

Tx prefix hash: 41f38f8ea195fbae54f3e1a0a1ec16b96100bccbacd0d38607f0c7323cea1602
Tx public key: a3faf6c0ad149da6b5b51fa70a0edb7355c41447a219352333417e82656a1ee7
Timestamp: 1711051123 Timestamp [UCT]: 2024-03-21 19:58:43 Age [y:d:h:m:s]: 00:281:20:19:40
Block: 983383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201737 RingCT/type: yes/0
Extra: 01a3faf6c0ad149da6b5b51fa70a0edb7355c41447a219352333417e82656a1ee702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cdb92c1c34aabc000a7d1f343552e2dc1facfea3afd63ab6199e7f3abf55a21 0.600000000000 1443510 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": 983393, "vin": [ { "gen": { "height": 983383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cdb92c1c34aabc000a7d1f343552e2dc1facfea3afd63ab6199e7f3abf55a21" } } ], "extra": [ 1, 163, 250, 246, 192, 173, 20, 157, 166, 181, 181, 31, 167, 10, 14, 219, 115, 85, 196, 20, 71, 162, 25, 53, 35, 51, 65, 126, 130, 101, 106, 30, 231, 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