Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff6cf8259a308406ecd5e6424f307ca902a3992cf1cfc79a790070edb2c8fb1

Tx prefix hash: 65a9e47bd7f768927b599b3b576cf4f0c25bb083677ecca15a84f8e77be5858b
Tx public key: 19087e4808ee2d3ab6d712a2c9b37f8c49a4b4aa36c064d0d931a26a08845250
Timestamp: 1590431623 Timestamp [UCT]: 2020-05-25 18:33:43 Age [y:d:h:m:s]: 05:165:04:10:32
Block: 103170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1302628 RingCT/type: yes/0
Extra: 0119087e4808ee2d3ab6d712a2c9b37f8c49a4b4aa36c064d0d931a26a0884525002110000032a25a1e897000000000000000000

1 output(s) for total of 279.354531217000 dcy

stealth address amount amount idx
00: 92a13fb18ee4a690439080c764dd5815356da9cabbde0bc81cfe064c49696be0 279.354531217000 181049 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": 103180, "vin": [ { "gen": { "height": 103170 } } ], "vout": [ { "amount": 279354531217, "target": { "key": "92a13fb18ee4a690439080c764dd5815356da9cabbde0bc81cfe064c49696be0" } } ], "extra": [ 1, 25, 8, 126, 72, 8, 238, 45, 58, 182, 215, 18, 162, 201, 179, 127, 140, 73, 164, 180, 170, 54, 192, 100, 208, 217, 49, 162, 106, 8, 132, 82, 80, 2, 17, 0, 0, 3, 42, 37, 161, 232, 151, 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