Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d09d7c499a24c8f8fc76dd11080a97ec79f2253bb6085ef76a92d88c17d0468c

Tx prefix hash: bf14ec62f06a4e4b1cb1f6e34ac3e4a0c8552a79ccd6a8c6e0e77ab78c0be7fd
Tx public key: b7dc99d6b0a5c5cd78ad66f25ef37a0d46d2695154324d581f8a189aff3ef02c
Timestamp: 1722025447 Timestamp [UCT]: 2024-07-26 20:24:07 Age [y:d:h:m:s]: 00:284:20:07:26
Block: 1074338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203510 RingCT/type: yes/0
Extra: 01b7dc99d6b0a5c5cd78ad66f25ef37a0d46d2695154324d581f8a189aff3ef02c021100000015e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8278da9f2313359c98bcf56e3288b5a4db91776c5bb1541fb6a9b607de36796a 0.600000000000 1546851 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": 1074348, "vin": [ { "gen": { "height": 1074338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8278da9f2313359c98bcf56e3288b5a4db91776c5bb1541fb6a9b607de36796a" } } ], "extra": [ 1, 183, 220, 153, 214, 176, 165, 197, 205, 120, 173, 102, 242, 94, 243, 122, 13, 70, 210, 105, 81, 84, 50, 77, 88, 31, 138, 24, 154, 255, 62, 240, 44, 2, 17, 0, 0, 0, 21, 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