Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbff2cd24041551ceb2054f34c298bd4cf3a3b41086d07f67ecd3a958f2785ca

Tx prefix hash: 6a58d9f2ebb5722829e0200af4969169481aeff654657fe893e4d8936bcf6a06
Tx public key: 67f4ae413e62d409463782aca14d23cbd2b130680f7a08e990aefa05bf098c2b
Timestamp: 1702944480 Timestamp [UCT]: 2023-12-19 00:08:00 Age [y:d:h:m:s]: 01:150:00:03:29
Block: 916156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368357 RingCT/type: yes/0
Extra: 0167f4ae413e62d409463782aca14d23cbd2b130680f7a08e990aefa05bf098c2b021100000002faf35c9c000000000000000000

1 output(s) for total of 0.605840000000 dcy

stealth address amount amount idx
00: 86ae03c7c4285a2db3bf41bc329aacb0735a7aef271b181b7965967e902b3b06 0.605840000000 1373634 of 0

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": 916166, "vin": [ { "gen": { "height": 916156 } } ], "vout": [ { "amount": 605840000, "target": { "key": "86ae03c7c4285a2db3bf41bc329aacb0735a7aef271b181b7965967e902b3b06" } } ], "extra": [ 1, 103, 244, 174, 65, 62, 98, 212, 9, 70, 55, 130, 172, 161, 77, 35, 203, 210, 177, 48, 104, 15, 122, 8, 233, 144, 174, 250, 5, 191, 9, 140, 43, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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