Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7b6adbdb581f1eb8007ef9cac39ba3ac6e8a156a3ab25d9a5f4023b56ef945f

Tx prefix hash: f327945a0887a9e4cf63ba43b0c505dc49114f059ebf0ed8e4befca79e522b25
Tx public key: c6751c68c6d805cee84fb72fa5578c1117fa34554eb5f2411e66100fc4c9fe5d
Timestamp: 1744066606 Timestamp [UCT]: 2025-04-07 22:56:46 Age [y:d:h:m:s]: 00:218:20:09:19
Block: 1256570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154139 RingCT/type: yes/0
Extra: 01c6751c68c6d805cee84fb72fa5578c1117fa34554eb5f2411e66100fc4c9fe5d021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a044b1ca1f72d076e5096a402fa5a817a30eb88854817f50d55af946021830d8 0.600000000000 1743685 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": 1256580, "vin": [ { "gen": { "height": 1256570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a044b1ca1f72d076e5096a402fa5a817a30eb88854817f50d55af946021830d8" } } ], "extra": [ 1, 198, 117, 28, 104, 198, 216, 5, 206, 232, 79, 183, 47, 165, 87, 140, 17, 23, 250, 52, 85, 78, 181, 242, 65, 30, 102, 16, 15, 196, 201, 254, 93, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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