Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993df16b90d7521bb743ebe52edbdc459e3be0ec0e73bad3e80df4d9cc9cb744

Tx prefix hash: 012d5e13b2676ea26e741ecd2a84157578541d081c3c1c5b27c42ac33600857c
Tx public key: b2c28bd1f5a795b1d36a8b2173e4b9686845870aaf5a0c2a26a59344d56b27a0
Timestamp: 1582438501 Timestamp [UCT]: 2020-02-23 06:15:01 Age [y:d:h:m:s]: 04:321:13:01:39
Block: 70717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122359 RingCT/type: yes/0
Extra: 01b2c28bd1f5a795b1d36a8b2173e4b9686845870aaf5a0c2a26a59344d56b27a0021100000001c71d3ff9000000000000000000

1 output(s) for total of 357.837643854000 dcy

stealth address amount amount idx
00: 6bdf013cd58cb17189d2db530eaedc964540994eb334e7ceffab43c39cacf7b5 357.837643854000 130657 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": 70727, "vin": [ { "gen": { "height": 70717 } } ], "vout": [ { "amount": 357837643854, "target": { "key": "6bdf013cd58cb17189d2db530eaedc964540994eb334e7ceffab43c39cacf7b5" } } ], "extra": [ 1, 178, 194, 139, 209, 245, 167, 149, 177, 211, 106, 139, 33, 115, 228, 185, 104, 104, 69, 135, 10, 175, 90, 12, 42, 38, 165, 147, 68, 213, 107, 39, 160, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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