Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7d185da75c97aa4e631a443d6d34f68442a030023fdd3fc57fdb0043a10336

Tx prefix hash: 03622ddfad45a2cc4f8a8839d181f54b5b457656b45fdb9a2f9f2d338af9200f
Tx public key: ff9c5d5a06f7f69926fe0a14e6bdde6eb517463e6452c32a9c2cfdba797db7e0
Timestamp: 1710299002 Timestamp [UCT]: 2024-03-13 03:03:22 Age [y:d:h:m:s]: 01:061:00:50:07
Block: 977140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304620 RingCT/type: yes/0
Extra: 01ff9c5d5a06f7f69926fe0a14e6bdde6eb517463e6452c32a9c2cfdba797db7e002110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f04d3941e8b56dc5f2927ced96844f900709bf348125a1200ea879d6c701539 0.600000000000 1437141 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": 977150, "vin": [ { "gen": { "height": 977140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f04d3941e8b56dc5f2927ced96844f900709bf348125a1200ea879d6c701539" } } ], "extra": [ 1, 255, 156, 93, 90, 6, 247, 246, 153, 38, 254, 10, 20, 230, 189, 222, 110, 181, 23, 70, 62, 100, 82, 195, 42, 156, 44, 253, 186, 121, 125, 183, 224, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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