Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342a67383665972a834dc5956fa504ff06c8fa154721fcb0e27038253a615c04

Tx prefix hash: 8fdfb1147c1f799f01b5327176424cb0d4b1b56a7755c4c15c1ca419e7dcacdc
Tx public key: 4ad29259970a94110157f3b9ef166beb1efafb00fc028bf11a844dfa6ec5ec4a
Timestamp: 1752012236 Timestamp [UCT]: 2025-07-08 22:03:56 Age [y:d:h:m:s]: 00:135:16:59:30
Block: 1321580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95440 RingCT/type: yes/0
Extra: 014ad29259970a94110157f3b9ef166beb1efafb00fc028bf11a844dfa6ec5ec4a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2676c9ea9f06f5d26c8d34f88f047874f2d8ead687d2003596aee86a62e5e963 0.600000000000 1809287 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": 1321590, "vin": [ { "gen": { "height": 1321580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2676c9ea9f06f5d26c8d34f88f047874f2d8ead687d2003596aee86a62e5e963" } } ], "extra": [ 1, 74, 210, 146, 89, 151, 10, 148, 17, 1, 87, 243, 185, 239, 22, 107, 235, 30, 250, 251, 0, 252, 2, 139, 241, 26, 132, 77, 250, 110, 197, 236, 74, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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