Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80096cb014a54969799e93b3e79608080a9a364758b89c2c0231cc8e7b299e39

Tx prefix hash: 45af2f1fd4f7b6f4c6486c06a569b1271a89e8d9a2f81338de354f7213830471
Tx public key: c0ef2288295d295861e410b549cd737e041ea9c6c1d8916607d106ed01837d26
Timestamp: 1725598637 Timestamp [UCT]: 2024-09-06 04:57:17 Age [y:d:h:m:s]: 00:244:01:03:07
Block: 1103978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174274 RingCT/type: yes/0
Extra: 01c0ef2288295d295861e410b549cd737e041ea9c6c1d8916607d106ed01837d26021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e74c64ea81dc1fb58538d475adf6d5931e7a4d4a773a0d648786065f79bf792 0.600000000000 1581013 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": 1103988, "vin": [ { "gen": { "height": 1103978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e74c64ea81dc1fb58538d475adf6d5931e7a4d4a773a0d648786065f79bf792" } } ], "extra": [ 1, 192, 239, 34, 136, 41, 93, 41, 88, 97, 228, 16, 181, 73, 205, 115, 126, 4, 30, 169, 198, 193, 216, 145, 102, 7, 209, 6, 237, 1, 131, 125, 38, 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