Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40bddc166dc25ebaf3c00cbc2518e6db3e6a1231e68266a994475f9dfd206049

Tx prefix hash: c17af4192776d827bd15937f653eb593e01932cefd2e86f5d4fecd1dae2a1c2a
Tx public key: 7cd6378f190980bb4e307b5ea210c7666b3b6ab67c09426cd2b8fb7c0649eaf8
Timestamp: 1737522586 Timestamp [UCT]: 2025-01-22 05:09:46 Age [y:d:h:m:s]: 00:146:19:56:23
Block: 1202632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104681 RingCT/type: yes/0
Extra: 017cd6378f190980bb4e307b5ea210c7666b3b6ab67c09426cd2b8fb7c0649eaf8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7911425b3fd527cad2a0c4e010824724973b1856458c7690db07a0295a2f2822 0.600000000000 1689297 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": 1202642, "vin": [ { "gen": { "height": 1202632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7911425b3fd527cad2a0c4e010824724973b1856458c7690db07a0295a2f2822" } } ], "extra": [ 1, 124, 214, 55, 143, 25, 9, 128, 187, 78, 48, 123, 94, 162, 16, 199, 102, 107, 59, 106, 182, 124, 9, 66, 108, 210, 184, 251, 124, 6, 73, 234, 248, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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