Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90dedd57ec1bfd5a6252524398a05170ed4a1e9b59cb87cde71e662ddb77f66e

Tx prefix hash: f4afca8fbe18ec9cb03094f9f0e32b9f48b1eae6c76d3b8e2a231319040fd4ff
Tx public key: 9b9952a20e4efb0e3c4fc3b7b2c59e77ba7b495e9498372bc8a0af3b9faabde4
Timestamp: 1709032830 Timestamp [UCT]: 2024-02-27 11:20:30 Age [y:d:h:m:s]: 01:019:01:30:51
Block: 966638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274645 RingCT/type: yes/0
Extra: 019b9952a20e4efb0e3c4fc3b7b2c59e77ba7b495e9498372bc8a0af3b9faabde40211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37db7a6b608f85ba31f4771aa6697e6150f0f298821a05ced484f3850babd62d 0.600000000000 1426405 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": 966648, "vin": [ { "gen": { "height": 966638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37db7a6b608f85ba31f4771aa6697e6150f0f298821a05ced484f3850babd62d" } } ], "extra": [ 1, 155, 153, 82, 162, 14, 78, 251, 14, 60, 79, 195, 183, 178, 197, 158, 119, 186, 123, 73, 94, 148, 152, 55, 43, 200, 160, 175, 59, 159, 170, 189, 228, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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