Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa35e760153a8395624c295ee4b3f0ec23c035a7bfd3e9da42781b3419d69ca1

Tx prefix hash: 21d8d85d057d802102fadfd296add2e89c9a606e1fce61fcaf79a9495913b497
Tx public key: a3e3d1ec53e3d05fefb30db348b5aca61bec8219e627a884d2ab4a1b988b9423
Timestamp: 1696635936 Timestamp [UCT]: 2023-10-06 23:45:36 Age [y:d:h:m:s]: 02:036:02:51:43
Block: 864054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545451 RingCT/type: yes/0
Extra: 01a3e3d1ec53e3d05fefb30db348b5aca61bec8219e627a884d2ab4a1b988b942302110000000233af99f4000000000000000000

1 output(s) for total of 0.841454133000 dcy

stealth address amount amount idx
00: dd6aa474c4e7401093133eddcc1bfe511c01e10a682644b58bfc267461fb774b 0.841454133000 1318560 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": 864064, "vin": [ { "gen": { "height": 864054 } } ], "vout": [ { "amount": 841454133, "target": { "key": "dd6aa474c4e7401093133eddcc1bfe511c01e10a682644b58bfc267461fb774b" } } ], "extra": [ 1, 163, 227, 209, 236, 83, 227, 208, 95, 239, 179, 13, 179, 72, 181, 172, 166, 27, 236, 130, 25, 230, 39, 168, 132, 210, 171, 74, 27, 152, 139, 148, 35, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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