Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c8a469f7d35dfd5674af04457f4166ae6566b6e325d14479df36bf560dfefc3

Tx prefix hash: c02a074fdd505f2d3577fb571b18093e76f7e450f09f0dc21371e6d8900775ef
Tx public key: 0b47f2c243e7ab5a93e0b1366b055532f6afeb224c5e12704463682b37fe4be8
Timestamp: 1751195507 Timestamp [UCT]: 2025-06-29 11:11:47 Age [y:d:h:m:s]: 00:145:10:07:48
Block: 1315158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102056 RingCT/type: yes/0
Extra: 010b47f2c243e7ab5a93e0b1366b055532f6afeb224c5e12704463682b37fe4be80211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bdbf270f178d04762c7cd32492840e9cbb55c8fc95c8f0d472eed5a64179b77 0.600000000000 1802811 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": 1315168, "vin": [ { "gen": { "height": 1315158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bdbf270f178d04762c7cd32492840e9cbb55c8fc95c8f0d472eed5a64179b77" } } ], "extra": [ 1, 11, 71, 242, 194, 67, 231, 171, 90, 147, 224, 177, 54, 107, 5, 85, 50, 246, 175, 235, 34, 76, 94, 18, 112, 68, 99, 104, 43, 55, 254, 75, 232, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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