Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f6a150ac179eab9ef50a88f09f3b6715eb13f32df3887e3bf4960a62a2d292

Tx prefix hash: 1e918514dd4b32faadf89cfb743292556ae6df2bd4f849e7fd08b2dbbefcfb4e
Tx public key: 0c2c7b36f601614515ef7ff751377ed09c24237de9033c074409763c68f2bb4e
Timestamp: 1745564697 Timestamp [UCT]: 2025-04-25 07:04:57 Age [y:d:h:m:s]: 00:210:17:26:09
Block: 1268994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148313 RingCT/type: yes/0
Extra: 010c2c7b36f601614515ef7ff751377ed09c24237de9033c074409763c68f2bb4e021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 772ed68bea08e7e4a3c252a65e13cabc0e611c2993a90b53956d4a17feb66326 0.600000000000 1756227 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": 1269004, "vin": [ { "gen": { "height": 1268994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "772ed68bea08e7e4a3c252a65e13cabc0e611c2993a90b53956d4a17feb66326" } } ], "extra": [ 1, 12, 44, 123, 54, 246, 1, 97, 69, 21, 239, 127, 247, 81, 55, 126, 208, 156, 36, 35, 125, 233, 3, 60, 7, 68, 9, 118, 60, 104, 242, 187, 78, 2, 17, 0, 0, 0, 4, 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