Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e92e840fd3b8edde3f2b9234e70fde476d5dfab1ec00812a412bace3f252abe

Tx prefix hash: f943754bbd2683c42520e5ed843aba6d089e1409c41a55dfbd4e99dbef38a789
Tx public key: c890867300ed97768e845c02b285d5cb2e1d3e7ee4515ae146889eaf7f79d4d4
Timestamp: 1746031679 Timestamp [UCT]: 2025-04-30 16:47:59 Age [y:d:h:m:s]: 00:251:20:52:11
Block: 1272840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177809 RingCT/type: yes/0
Extra: 01c890867300ed97768e845c02b285d5cb2e1d3e7ee4515ae146889eaf7f79d4d40211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f489f24d7ee1abdd882dac2073346f000acbdf619539f91a540fd1cc911001 0.600000000000 1760115 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": 1272850, "vin": [ { "gen": { "height": 1272840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f489f24d7ee1abdd882dac2073346f000acbdf619539f91a540fd1cc911001" } } ], "extra": [ 1, 200, 144, 134, 115, 0, 237, 151, 118, 142, 132, 92, 2, 178, 133, 213, 203, 46, 29, 62, 126, 228, 81, 90, 225, 70, 136, 158, 175, 127, 121, 212, 212, 2, 17, 0, 0, 0, 1, 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