Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8490c5ecac2dc544428a2e688f7f1508eb9b6932fd3d8f22e06292cffb2d7f0d

Tx prefix hash: 327cfe892349f1955be1bbcbaff1a6389edc6f779ef8152fdb2b90bf9268b14d
Tx public key: a7ec97edd313908bcfa9b3c588f250e9ee05d1f6f6db05ed84d181a9f8088399
Timestamp: 1749644386 Timestamp [UCT]: 2025-06-11 12:19:46 Age [y:d:h:m:s]: 00:151:19:17:53
Block: 1302762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106175 RingCT/type: yes/0
Extra: 01a7ec97edd313908bcfa9b3c588f250e9ee05d1f6f6db05ed84d181a9f80883990211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d17d1e26b2bcb09062604410909e85a2c7ea2d5c4231325342ff89364ba1e9fd 0.600000000000 1790335 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": 1302772, "vin": [ { "gen": { "height": 1302762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d17d1e26b2bcb09062604410909e85a2c7ea2d5c4231325342ff89364ba1e9fd" } } ], "extra": [ 1, 167, 236, 151, 237, 211, 19, 144, 139, 207, 169, 179, 197, 136, 242, 80, 233, 238, 5, 209, 246, 246, 219, 5, 237, 132, 209, 129, 169, 248, 8, 131, 153, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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