Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7603a6744da2746ccbc4e5663a797dd6e786e2fc2bf43cd95a87354ef021270

Tx prefix hash: 92f48236f0d1b94e6bb45c36cc273f702d6fdaddce58ae1855f333610e397abf
Tx public key: ed3178c5e19d3081da392a0b95f7f98453cb71e9e67edc07ee3a5e08a2e4adb0
Timestamp: 1745544591 Timestamp [UCT]: 2025-04-25 01:29:51 Age [y:d:h:m:s]: 00:209:20:56:53
Block: 1268819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147711 RingCT/type: yes/0
Extra: 01ed3178c5e19d3081da392a0b95f7f98453cb71e9e67edc07ee3a5e08a2e4adb0021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7377f12d011a9929e52247f8a9ba7e30dd5f153bc131a8bf88bab0ecd34f2a1d 0.600000000000 1756052 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": 1268829, "vin": [ { "gen": { "height": 1268819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7377f12d011a9929e52247f8a9ba7e30dd5f153bc131a8bf88bab0ecd34f2a1d" } } ], "extra": [ 1, 237, 49, 120, 197, 225, 157, 48, 129, 218, 57, 42, 11, 149, 247, 249, 132, 83, 203, 113, 233, 230, 126, 220, 7, 238, 58, 94, 8, 162, 228, 173, 176, 2, 17, 0, 0, 0, 1, 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