Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362c69915fb759fc254c91d826c3b5fc59858ef16383e51aa5c52a1e0c373648

Tx prefix hash: f2b3397482ee824b0c5740029326cc4fc7dd941bcbcc5af646c6351e87d4ef3a
Tx public key: a5e971d47df21da0448fb975282ea0f0aff72da713aca4b1e00411fe64b89389
Timestamp: 1759426788 Timestamp [UCT]: 2025-10-02 17:39:48 Age [y:d:h:m:s]: 00:005:16:34:12
Block: 1381302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4064 RingCT/type: yes/0
Extra: 01a5e971d47df21da0448fb975282ea0f0aff72da713aca4b1e00411fe64b8938902110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9459b469d26a056d0ae57cbb6c53d933d01f4fc107637d192d242550e1f8e0a4 0.600000000000 1869421 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": 1381312, "vin": [ { "gen": { "height": 1381302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9459b469d26a056d0ae57cbb6c53d933d01f4fc107637d192d242550e1f8e0a4" } } ], "extra": [ 1, 165, 233, 113, 212, 125, 242, 29, 160, 68, 143, 185, 117, 40, 46, 160, 240, 175, 247, 45, 167, 19, 172, 164, 177, 224, 4, 17, 254, 100, 184, 147, 137, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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