Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33ef695e82b128190ec5589da0e2c52395d06cf6f08681a33292479f9bc49b1

Tx prefix hash: 541f804526335284ff4163c4e0a9fec4686b908e287e19767a922bf368e263b9
Tx public key: 32d91960d91018933c8f98e40a2ae1e4e6e992ccd328f291de9449283ee34ab3
Timestamp: 1751225764 Timestamp [UCT]: 2025-06-29 19:36:04 Age [y:d:h:m:s]: 00:142:21:25:39
Block: 1315363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100295 RingCT/type: yes/0
Extra: 0132d91960d91018933c8f98e40a2ae1e4e6e992ccd328f291de9449283ee34ab3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 387a38d6c78e0ef129f7066f827311c8bb8f7408a4a2185a5620cb44a53edbe6 0.600000000000 1803018 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": 1315373, "vin": [ { "gen": { "height": 1315363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "387a38d6c78e0ef129f7066f827311c8bb8f7408a4a2185a5620cb44a53edbe6" } } ], "extra": [ 1, 50, 217, 25, 96, 217, 16, 24, 147, 60, 143, 152, 228, 10, 42, 225, 228, 230, 233, 146, 204, 211, 40, 242, 145, 222, 148, 73, 40, 62, 227, 74, 179, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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