Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f62af60eada8d628f782dc30e2fb3ba95efcb8fb62f545ce616acf20f4d8b60e

Tx prefix hash: 02699be966d5c6deb5c2ef3cee5b1ee124269a2d355efe5ef0d5bb631bf8389e
Tx public key: 71a71650fac8e1cd6205c2a916e518cc4a6b80d06cbafd45e5f76c455230e1f9
Timestamp: 1735816762 Timestamp [UCT]: 2025-01-02 11:19:22 Age [y:d:h:m:s]: 00:167:04:25:08
Block: 1188548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119198 RingCT/type: yes/0
Extra: 0171a71650fac8e1cd6205c2a916e518cc4a6b80d06cbafd45e5f76c455230e1f9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43dff28861ca7a99d163406dc8259f4deea2a126fb51e4d852fff5b10e71ade9 0.600000000000 1675051 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": 1188558, "vin": [ { "gen": { "height": 1188548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43dff28861ca7a99d163406dc8259f4deea2a126fb51e4d852fff5b10e71ade9" } } ], "extra": [ 1, 113, 167, 22, 80, 250, 200, 225, 205, 98, 5, 194, 169, 22, 229, 24, 204, 74, 107, 128, 208, 108, 186, 253, 69, 229, 247, 108, 69, 82, 48, 225, 249, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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