Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adc88e6ae11199c4ed893728d43ae550751c8f39068010cd55b27475b7c5698f

Tx prefix hash: 39efaa37b17bb13c23ec4f2474dc025c75c3f1961c4e80da4f7ff19394c22668
Tx public key: 5065d62965aa48551aa49f7add4e937b8313f789f38cdd1b9bffad919bfebe40
Timestamp: 1700413023 Timestamp [UCT]: 2023-11-19 16:57:03 Age [y:d:h:m:s]: 01:141:03:16:42
Block: 895170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362036 RingCT/type: yes/0
Extra: 015065d62965aa48551aa49f7add4e937b8313f789f38cdd1b9bffad919bfebe40021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.663636368000 dcy

stealth address amount amount idx
00: f2e950cc4791c555065fb5a425d02d81b64c17557841c431fd9614267460f241 0.663636368000 1351393 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": 895180, "vin": [ { "gen": { "height": 895170 } } ], "vout": [ { "amount": 663636368, "target": { "key": "f2e950cc4791c555065fb5a425d02d81b64c17557841c431fd9614267460f241" } } ], "extra": [ 1, 80, 101, 214, 41, 101, 170, 72, 85, 26, 164, 159, 122, 221, 78, 147, 123, 131, 19, 247, 137, 243, 140, 221, 27, 155, 255, 173, 145, 155, 254, 190, 64, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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