Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c705a18e20fb670fa989b18b37017dea2496099e76e71e557afe8dab7d761ea4

Tx prefix hash: 6f110b553c2bb36c43cebe427b6e8ebb2dc7e5016ea2c8f555427eea455d0a35
Tx public key: f98867c63704bb4b6e246d954500ad313778cb71bd2ff3172a9dc5f88300e26b
Timestamp: 1721713447 Timestamp [UCT]: 2024-07-23 05:44:07 Age [y:d:h:m:s]: 00:269:00:04:19
Block: 1071753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192186 RingCT/type: yes/0
Extra: 01f98867c63704bb4b6e246d954500ad313778cb71bd2ff3172a9dc5f88300e26b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdd1b0b3655c3830e6002f72890a1f8b1d100dedd2ab0ade62c2fc6dcb17cf9f 0.600000000000 1544096 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": 1071763, "vin": [ { "gen": { "height": 1071753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdd1b0b3655c3830e6002f72890a1f8b1d100dedd2ab0ade62c2fc6dcb17cf9f" } } ], "extra": [ 1, 249, 136, 103, 198, 55, 4, 187, 75, 110, 36, 109, 149, 69, 0, 173, 49, 55, 120, 203, 113, 189, 47, 243, 23, 42, 157, 197, 248, 131, 0, 226, 107, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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