Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ea80456b1494dda4a1f6acd53eceb0da64370555d94fd1e4e6bbc408e2db75b

Tx prefix hash: f2c6348ba5bc423b260346d6777dc4a4fe8badae6fe600dc5456189dac9d09f7
Tx public key: 50a87514a95f05d4ad7226ce892ef38224c42dca6f1607ccefef6cc6cdd963a3
Timestamp: 1722003773 Timestamp [UCT]: 2024-07-26 14:22:53 Age [y:d:h:m:s]: 00:257:01:51:42
Block: 1074169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183639 RingCT/type: yes/0
Extra: 0150a87514a95f05d4ad7226ce892ef38224c42dca6f1607ccefef6cc6cdd963a3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61159895afd3884e91053ec8c535a2c22cb5c9fbfe23823270a46aa2e8545433 0.600000000000 1546682 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": 1074179, "vin": [ { "gen": { "height": 1074169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61159895afd3884e91053ec8c535a2c22cb5c9fbfe23823270a46aa2e8545433" } } ], "extra": [ 1, 80, 168, 117, 20, 169, 95, 5, 212, 173, 114, 38, 206, 137, 46, 243, 130, 36, 196, 45, 202, 111, 22, 7, 204, 239, 239, 108, 198, 205, 217, 99, 163, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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