Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ddfeaac8f7426b0ae589c1b958419ade3e2dd85fcd52e593574b8257f3b0dbc

Tx prefix hash: 01683015e4875bd532ff02fb4d36997b40f125c56b9b69488cce21b9fc50998b
Tx public key: c5f3e6dbc5aaa57189bdc7a4d4b3cb6a2181420af58dfa136c7f06924f16c814
Timestamp: 1718671319 Timestamp [UCT]: 2024-06-18 00:41:59 Age [y:d:h:m:s]: 00:167:10:03:32
Block: 1046545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119817 RingCT/type: yes/0
Extra: 01c5f3e6dbc5aaa57189bdc7a4d4b3cb6a2181420af58dfa136c7f06924f16c8140211000000010bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff7cb4f1cc085dc928eb1ba9029d889700dd4964622681b4645d507bf9af81e8 0.600000000000 1516360 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": 1046555, "vin": [ { "gen": { "height": 1046545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff7cb4f1cc085dc928eb1ba9029d889700dd4964622681b4645d507bf9af81e8" } } ], "extra": [ 1, 197, 243, 230, 219, 197, 170, 165, 113, 137, 189, 199, 164, 212, 179, 203, 106, 33, 129, 66, 10, 245, 141, 250, 19, 108, 127, 6, 146, 79, 22, 200, 20, 2, 17, 0, 0, 0, 1, 11, 186, 22, 215, 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