Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f50fcbaabd4ed748f58a722ea3ebff214cbbc4da9ff8cb5e93db9db663a99e02

Tx prefix hash: 90cc8b4abed0ae34ab78c93516c748ebd94dcde70c8afb7400b2f53ee3658fb5
Tx public key: ce04dedaa776641c0eb800a5e56088df40370f7b5bfd5eb874596f9556157bc1
Timestamp: 1710439303 Timestamp [UCT]: 2024-03-14 18:01:43 Age [y:d:h:m:s]: 01:059:07:12:14
Block: 978310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303373 RingCT/type: yes/0
Extra: 01ce04dedaa776641c0eb800a5e56088df40370f7b5bfd5eb874596f9556157bc102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c0bc2d06c6e67a695e26ec4c9750ec939d0a5e8852df7cb2993bd733a655c6 0.600000000000 1438333 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": 978320, "vin": [ { "gen": { "height": 978310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c0bc2d06c6e67a695e26ec4c9750ec939d0a5e8852df7cb2993bd733a655c6" } } ], "extra": [ 1, 206, 4, 222, 218, 167, 118, 100, 28, 14, 184, 0, 165, 229, 96, 136, 223, 64, 55, 15, 123, 91, 253, 94, 184, 116, 89, 111, 149, 86, 21, 123, 193, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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