Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddb9ebe0ff2254261e6113533907993992aa88c86e06cacf46e96288628a5f40

Tx prefix hash: 3f984fd53c4e223050d6d2a4e51608752ecfe99696ac90eb1e90a56fbc58d316
Tx public key: 63f2081bc3e4a6e24f7862bbb9eb51185ff2acc4dfcf1036045073b6a9c02aa5
Timestamp: 1753384565 Timestamp [UCT]: 2025-07-24 19:16:05 Age [y:d:h:m:s]: 00:191:16:39:52
Block: 1332563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135744 RingCT/type: yes/0
Extra: 0163f2081bc3e4a6e24f7862bbb9eb51185ff2acc4dfcf1036045073b6a9c02aa5021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863d7a8c59e44b7da828b381023d039abd6e32ca14601672bb19a0c577a8f16d 0.600000000000 1820360 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": 1332573, "vin": [ { "gen": { "height": 1332563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863d7a8c59e44b7da828b381023d039abd6e32ca14601672bb19a0c577a8f16d" } } ], "extra": [ 1, 99, 242, 8, 27, 195, 228, 166, 226, 79, 120, 98, 187, 185, 235, 81, 24, 95, 242, 172, 196, 223, 207, 16, 54, 4, 80, 115, 182, 169, 192, 42, 165, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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