Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95ca02e9998e9bed60131d920556fd4b381379d40d87664abd5f216c97670a9a

Tx prefix hash: 8014fff2283fc055f559fa5c4e1bd31c08f0ebe46993a7c7bad8f68954c3f368
Tx public key: f4fb4ec9b794aaf1a18c283a4a6043fa941b6d07d484ecbd1180ee094395caa3
Timestamp: 1736921085 Timestamp [UCT]: 2025-01-15 06:04:45 Age [y:d:h:m:s]: 00:154:14:20:44
Block: 1197696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110188 RingCT/type: yes/0
Extra: 01f4fb4ec9b794aaf1a18c283a4a6043fa941b6d07d484ecbd1180ee094395caa30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9502676dd8ac3b55c707650d49f2e5ffc44ebd8a3e852aea0b3eae9f421a9618 0.600000000000 1684309 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": 1197706, "vin": [ { "gen": { "height": 1197696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9502676dd8ac3b55c707650d49f2e5ffc44ebd8a3e852aea0b3eae9f421a9618" } } ], "extra": [ 1, 244, 251, 78, 201, 183, 148, 170, 241, 161, 140, 40, 58, 74, 96, 67, 250, 148, 27, 109, 7, 212, 132, 236, 189, 17, 128, 238, 9, 67, 149, 202, 163, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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