Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59aed43913f248024608b5b8d7f4eb4d7bdf54bceecdb363e88c6fa8a9f035da

Tx prefix hash: c2b6d1dd6692cb22343ab7c0d091974c364bb775dcc3aecb28759a59b5796ee7
Tx public key: 2023bf3dcc3d38f13fd52dd76ad4d09113e5f6f29465b4b69090650d63690fd7
Timestamp: 1723296652 Timestamp [UCT]: 2024-08-10 13:30:52 Age [y:d:h:m:s]: 00:235:02:56:19
Block: 1084890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167920 RingCT/type: yes/0
Extra: 012023bf3dcc3d38f13fd52dd76ad4d09113e5f6f29465b4b69090650d63690fd7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e245e0c336635e42cf0b633e0862cf589cc2cd87152dbb3d204e0d21e6fee48 0.600000000000 1559325 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": 1084900, "vin": [ { "gen": { "height": 1084890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e245e0c336635e42cf0b633e0862cf589cc2cd87152dbb3d204e0d21e6fee48" } } ], "extra": [ 1, 32, 35, 191, 61, 204, 61, 56, 241, 63, 213, 45, 215, 106, 212, 208, 145, 19, 229, 246, 242, 148, 101, 180, 182, 144, 144, 101, 13, 99, 105, 15, 215, 2, 17, 0, 0, 0, 6, 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