Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e6da7b622844199a2b3f74ae65ac73a2bbb90df1acac149d23365bbd54d2da8

Tx prefix hash: c1c0d66a09210b2d2f3f984b7d12fe9e5a2b51461fa0c627fd88c321d06d2b37
Tx public key: dfdbb0b3d710e0759dfd2001cb503ba1de7be8befda0a813d21647d4c6e550f7
Timestamp: 1748282881 Timestamp [UCT]: 2025-05-26 18:08:01 Age [y:d:h:m:s]: 00:174:03:21:06
Block: 1291496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122142 RingCT/type: yes/0
Extra: 01dfdbb0b3d710e0759dfd2001cb503ba1de7be8befda0a813d21647d4c6e550f702110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99f9ff18aac6c7690eb7746bff1deb3087c59aaaf0db4a2b0707ed4eb29b1fb3 0.600000000000 1778967 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": 1291506, "vin": [ { "gen": { "height": 1291496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99f9ff18aac6c7690eb7746bff1deb3087c59aaaf0db4a2b0707ed4eb29b1fb3" } } ], "extra": [ 1, 223, 219, 176, 179, 215, 16, 224, 117, 157, 253, 32, 1, 203, 80, 59, 161, 222, 123, 232, 190, 253, 160, 168, 19, 210, 22, 71, 212, 198, 229, 80, 247, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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