Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 908e881df4d697352427cf2120b0ac01f328d9609e4ba921f2814e45e8ef4081

Tx prefix hash: 66ff2ca164fb5bde777c7fc04c029a8367a8cdcbd9ee8d0beca502578ea44172
Tx public key: 25ef879f715bfa8134768966f2e016d2a6f5b80b3c69a1da42a6664dd71e08df
Timestamp: 1682347001 Timestamp [UCT]: 2023-04-24 14:36:41 Age [y:d:h:m:s]: 01:263:04:09:45
Block: 745641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449568 RingCT/type: yes/0
Extra: 0125ef879f715bfa8134768966f2e016d2a6f5b80b3c69a1da42a6664dd71e08df021100000003b3164c24000000000000000000

1 output(s) for total of 2.076739609000 dcy

stealth address amount amount idx
00: 045f966c82f51cffd0b3cd8311e94e6e80d24fce711dacc405829221921945f3 2.076739609000 1193110 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": 745651, "vin": [ { "gen": { "height": 745641 } } ], "vout": [ { "amount": 2076739609, "target": { "key": "045f966c82f51cffd0b3cd8311e94e6e80d24fce711dacc405829221921945f3" } } ], "extra": [ 1, 37, 239, 135, 159, 113, 91, 250, 129, 52, 118, 137, 102, 242, 224, 22, 210, 166, 245, 184, 11, 60, 105, 161, 218, 66, 166, 102, 77, 215, 30, 8, 223, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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