Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b982090f17811fd2f3b9ba6ed38dd5354ba2e860b74c18fce5b0bc205ca43f14

Tx prefix hash: 36e528f0a353404fc438e25e86cd20166e64e68739d4e17b4c649a76ff31e3a4
Tx public key: 4e60485d403fbe71be27566e74f6c7e0e6cfceaf70e48d8ca56190abc5d763c8
Timestamp: 1746408222 Timestamp [UCT]: 2025-05-05 01:23:42 Age [y:d:h:m:s]: 00:199:18:51:22
Block: 1275961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140500 RingCT/type: yes/0
Extra: 014e60485d403fbe71be27566e74f6c7e0e6cfceaf70e48d8ca56190abc5d763c80211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2d069132f4cff1e15b1c14bb82f3d188581fccab3b61090fb498bf78a836207 0.600000000000 1763276 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": 1275971, "vin": [ { "gen": { "height": 1275961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2d069132f4cff1e15b1c14bb82f3d188581fccab3b61090fb498bf78a836207" } } ], "extra": [ 1, 78, 96, 72, 93, 64, 63, 190, 113, 190, 39, 86, 110, 116, 246, 199, 224, 230, 207, 206, 175, 112, 228, 141, 140, 165, 97, 144, 171, 197, 215, 99, 200, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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