Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4260142f67832dd9e451d7d7d4feb97fb020e43396fd538d62e2a08446580a8c

Tx prefix hash: 0329393e9cb32324458e91c91617437109bbd562a7777296f9a763f5b5d1b944
Tx public key: e9a2d558f2262a7cbb591f711a1dfd207a508042d5d462ceb063d52998fd89db
Timestamp: 1766172304 Timestamp [UCT]: 2025-12-19 19:25:04 Age [y:d:h:m:s]: 00:002:01:25:43
Block: 1437214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1462 RingCT/type: yes/0
Extra: 01e9a2d558f2262a7cbb591f711a1dfd207a508042d5d462ceb063d52998fd89db0211000000057b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7616e64e6e886057ff12cf1fcbf2b44984cd865152c0931fc3d19ad977c9f8fd 0.600000000000 1926021 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": 1437224, "vin": [ { "gen": { "height": 1437214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7616e64e6e886057ff12cf1fcbf2b44984cd865152c0931fc3d19ad977c9f8fd" } } ], "extra": [ 1, 233, 162, 213, 88, 242, 38, 42, 124, 187, 89, 31, 113, 26, 29, 253, 32, 122, 80, 128, 66, 213, 212, 98, 206, 176, 99, 213, 41, 152, 253, 137, 219, 2, 17, 0, 0, 0, 5, 123, 30, 81, 172, 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