Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c7b2edae7ace607d8ff251bfd6a5462de5da9ff1ab36f7b030ac06f9930883

Tx prefix hash: 65257399012678775fb95cdffc46d1dce14a8c4061f0293a242072bc0c1237f1
Tx public key: 0d118cb9ed748cf19c03e01bb6bb4f89c18fd6b719174c5134aadc5dc24dc088
Timestamp: 1755557719 Timestamp [UCT]: 2025-08-18 22:55:19 Age [y:d:h:m:s]: 00:044:20:49:54
Block: 1349467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31897 RingCT/type: yes/0
Extra: 010d118cb9ed748cf19c03e01bb6bb4f89c18fd6b719174c5134aadc5dc24dc088021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a45877c11824f3eb76b031fa90a4dcbbb80ee1acd7760430ca3022d134c8d0 0.600000000000 1837400 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": 1349477, "vin": [ { "gen": { "height": 1349467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a45877c11824f3eb76b031fa90a4dcbbb80ee1acd7760430ca3022d134c8d0" } } ], "extra": [ 1, 13, 17, 140, 185, 237, 116, 140, 241, 156, 3, 224, 27, 182, 187, 79, 137, 193, 143, 214, 183, 25, 23, 76, 81, 52, 170, 220, 93, 194, 77, 192, 136, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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