Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be161d2f9b67c61d2f55067f149c01a13fee0a4b989d81d1e1377e1cbf75342

Tx prefix hash: 429ca9dd4ec331d68fdf0487594bbd60e2d435bec09ed5acda73a4d5ca37af89
Tx public key: 5f8b92fed4dda542ba96c061ca79d682429b9d95cf7a6e80da80aae51e934b90
Timestamp: 1709943116 Timestamp [UCT]: 2024-03-09 00:11:56 Age [y:d:h:m:s]: 01:054:19:40:12
Block: 974188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300187 RingCT/type: yes/0
Extra: 015f8b92fed4dda542ba96c061ca79d682429b9d95cf7a6e80da80aae51e934b900211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7ea82e6a0c0261778acd1a56ded4e3e848ba347de6d559089dbde72e1d39bf2 0.600000000000 1434141 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": 974198, "vin": [ { "gen": { "height": 974188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7ea82e6a0c0261778acd1a56ded4e3e848ba347de6d559089dbde72e1d39bf2" } } ], "extra": [ 1, 95, 139, 146, 254, 212, 221, 165, 66, 186, 150, 192, 97, 202, 121, 214, 130, 66, 155, 157, 149, 207, 122, 110, 128, 218, 128, 170, 229, 30, 147, 75, 144, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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