Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc502d3f579f29372b9cbe612a87bea543455a1211107a884fe7465fee38379c

Tx prefix hash: 1430c702ddb0018aec993c5caa8edd9bd472da25a74765b939ca11285fe01f5c
Tx public key: cb6060461a1e7fc39cb63c1b6050db4bbdead31d3e0ea19ad246b9ab9df446e5
Timestamp: 1751249124 Timestamp [UCT]: 2025-06-30 02:05:24 Age [y:d:h:m:s]: 00:143:06:13:39
Block: 1315544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100570 RingCT/type: yes/0
Extra: 01cb6060461a1e7fc39cb63c1b6050db4bbdead31d3e0ea19ad246b9ab9df446e50211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d2c7f08e529eff4102da5d086681201732b7e84a362963b67d8b9d3a5b805d6 0.600000000000 1803199 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": 1315554, "vin": [ { "gen": { "height": 1315544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2c7f08e529eff4102da5d086681201732b7e84a362963b67d8b9d3a5b805d6" } } ], "extra": [ 1, 203, 96, 96, 70, 26, 30, 127, 195, 156, 182, 60, 27, 96, 80, 219, 75, 189, 234, 211, 29, 62, 14, 161, 154, 210, 70, 185, 171, 157, 244, 70, 229, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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