Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd752064200145cf8eacb0f22a6fdc2e2ef578e1cb54573e2636aec50931d89e

Tx prefix hash: 38570a029e4a97b61ec06c92329bc12e0897c171f3e176e1b0a5c22c95bf6bc3
Tx public key: 23f7b3e69aed35787e0f20b2cd1eb6352ffe843da3bddb2d253352b46ca31194
Timestamp: 1764999310 Timestamp [UCT]: 2025-12-06 05:35:10 Age [y:d:h:m:s]: 00:051:22:51:20
Block: 1427479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37029 RingCT/type: yes/0
Extra: 0123f7b3e69aed35787e0f20b2cd1eb6352ffe843da3bddb2d253352b46ca31194021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6910f0571927cb2226f1261723ecf22f7b432b0bbef593e51583c2ce784607f 0.600000000000 1916180 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": 1427489, "vin": [ { "gen": { "height": 1427479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6910f0571927cb2226f1261723ecf22f7b432b0bbef593e51583c2ce784607f" } } ], "extra": [ 1, 35, 247, 179, 230, 154, 237, 53, 120, 126, 15, 32, 178, 205, 30, 182, 53, 47, 254, 132, 61, 163, 189, 219, 45, 37, 51, 82, 180, 108, 163, 17, 148, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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