Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99c1b3d3e7c8b906755cb7b0842949c6ad431f4dadfdda636c32cca7382b2d74

Tx prefix hash: bc16e067ba0a2302ee94e956bf56a9e5fd7c62f36d3aeb671409abc72d5eade1
Tx public key: ba7fb9e8a6f8922bdb98647b6293d8193261e438f1a38480ae1088e646af5e53
Timestamp: 1699060004 Timestamp [UCT]: 2023-11-04 01:06:44 Age [y:d:h:m:s]: 01:202:12:07:24
Block: 884161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405756 RingCT/type: yes/0
Extra: 01ba7fb9e8a6f8922bdb98647b6293d8193261e438f1a38480ae1088e646af5e5302110000000775e3f0e9000000000000000000

1 output(s) for total of 0.721784549000 dcy

stealth address amount amount idx
00: f54a5ba970bff8e5ae4cb1e197497c16cf961584eed6b2df583daf732c5d1ff7 0.721784549000 1339894 of 0

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": 884171, "vin": [ { "gen": { "height": 884161 } } ], "vout": [ { "amount": 721784549, "target": { "key": "f54a5ba970bff8e5ae4cb1e197497c16cf961584eed6b2df583daf732c5d1ff7" } } ], "extra": [ 1, 186, 127, 185, 232, 166, 248, 146, 43, 219, 152, 100, 123, 98, 147, 216, 25, 50, 97, 228, 56, 241, 163, 132, 128, 174, 16, 136, 230, 70, 175, 94, 83, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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